Connecting to Individual VMs via SSH
Once access has been granted, you may SSH into the individual VMs. How to SSH in to a VM depends on which machine you want to connect to.
ssh [alias]@[public-ip] -p 22[vmid]
- Your alias can be found by referencing the Users page.
- The public-ip and vmid for a particular server can be found on the Server List page.
For example:
My alias: doej
Server information:
| Name | vmid | IP (Public) | IP (LAN) | Ports forwarded | Server Page. |
|---|---|---|---|---|---|
| ServiceX | 107 | 136.243.40.234 | 10.35.12.0 | 22107 (ssh), 80 (nginx), 443 (nginx) | Fictitious Server. |
To connect:
ssh doej@136.243.40.234 -p 22107
SSH Tunnelling and X forwarding should all work as expected. Port 22, the standard SSH port, is reserved for the host machine, the operating system in which all the VMs are run.
Connecting to host and forwarding your connection.
If you have access to the host operating system you can also connect to that on port 22, then SSH via the internal network.
For example, to internally connect to the webserver from the host system:
ssh doej@10.0.0.0 -p 22100
Connecting from the Trinity network
If you have tried to connect to any of the VMs from Trinity's network you might have noticed that you're not able to, this is because Trinity blocks SSH on non-standard (i.e., other than 22) ports, which we reserve for the host system.
For the moment the host system is using Port 22 although in the near future we will be setting up a simple jailed jump host on port 22 which you can use. For the moment you can request temporary access to Proxmox from which you can SSH into the internal network.
Good SSH Clients
If you're on a Mac or Linux device, the built in ssh command is sufficient.
For Windows, Bitvise is strongly recommend, as It comes bundled with an SFTP client (allowing you to graphically transfer files via SSH) and an RDP Client (for use of Xserver/Windows VMs if added).